Question

PM-action: percentage of cost in generated work task

  • 24 February 2022
  • 2 replies
  • 101 views
A
Rank
Userlevel 2
Badge +6

Hi,

We upgraded from apps 8 to apps 10 recently.

In apps 8 I could give a percentage of cost on a route pm action to enable split of cost according to the PMs actual cost.

I cannot seem to find this functionality in apps 10 and it is critical for us for instance when posting an invoice on a generated work task where one work task step represents 90 percent of the cost.

 

Anybody got a solution?

 

Best

Anders

This topic has been closed for comments

2 replies

Nethmini Kosvinna
Rank
Userlevel 6
Badge +18

Hi @Anders Jansson ,

Would you mind sending us more details of the issue with screen prints in order to understand your issue more clearly. We would like to know the flow you have practiced in APP8(with screen prints) so that we can see how to map it with APP10 functionality.

Thanks in advance

Best regards,

Nethmini

https://www.linkedin.com/in/nethmini-rathsala-kosvinna-8371b6127/
P
Rank
Userlevel 3
Badge +3

Hi @Anders Jansson,

In version APP10 the Route PM Actions was removed and instead two new ways was introduced as replacement, ‘Group’ and ‘Merge’.

The 'Group' concept is more advanced than the old Route handling and the 'Merge' concept is more simple than the old Route handling.

 

'Group'

  • Used by adding a value in 'PM Group ID' but no 'Merge' flag set.
  • The 'Group' concept is to be seen as the main option for the old route handling if you have use for more advanced "route" handling.
  • All Work List lines from one or more PM Actions will become Work Tasks on the generated Work Order.
  • The execution will be done on Work Task level.
  • For PM Actions using 'Group' you will get the exact costs reported back into the Actual Equipment Object on the Work Task.

 

 'Merge'

  • Used by adding a value in 'PM Group ID' and the 'Merge' flag set.
  • The 'Merge' concept is only to be used for simpler actions that you want to perform as a part of a list together with other similar simpler tasks as a checklist. As example for simpler inspections or lubrication rounds etc. where you not need instructions down on step level. This is also a reason for why a lot of criteria need to be met to fulfill a merge.
  • All Work List lines from one or more PM Actions (max one WL per PM) will in this case become a Work Task Step underneath same 'merge' Work Task on the generated Work Order. This 'merge' Work Task will be created just by the purpose to be a holder for the Work Task Steps created.
  • The execution will be done on Work Task step level.
  • For PM Actions using 'Merge' you will only get an equal share of the costs reported back into each of the Actual Equipment Objects on the Work Task Steps.
  • If entering an Actual Equipment Object on the 'merge' Work Task itself, this Actual Equipment Object will take the entire cost.

 

As a general recommendation from RnD it’s recommended to run PM Actions with 'Group' (but no 'Merge') when the PM Actions require more preparation, instructions etc. Here you will have all the required data available on the Work Task level and you will get the exact costs reported back to Actual Equipment Object on the Work Task. On the other hand running PM Actions with 'Merge' there will be a simpler handling but all data and exact follow up will not be available in this flow.

 

Best Regards
Pelle

Terms & ConditionsCookie settings